🤖 [RHTAS-build-bot] [main] Update FBC images - rhtas-operator #208
Open
🤖 [RHTAS-build-bot] [main] Update FBC images - rhtas-operator #208
Conversation
Reviewer's GuideThis PR updates the rhtas-operator FBC graphs and catalogs for OCP versions 4.16–4.20 to add the new bundle version v1.3.2, wiring it into all relevant channels with correct replaces/skips metadata and image digest. Flow diagram for rhtas_operator v1_3_x upgrade graph after adding v1_3_2flowchart LR
subgraph stable_v1_3_channel
b130_s[bundle rhtas-operator v1.3.0]
b131_s[bundle rhtas-operator v1.3.1]
b132_s[bundle rhtas-operator v1.3.2]
b130_s -->|replaced_by| b131_s
b130_s -->|replaced_by| b132_s
b132_s -.skips.-> b130_s
b132_s -.skips.-> b131_s
end
subgraph stable_channel
b120[bundle rhtas-operator v1.2.0]
b121[bundle rhtas-operator v1.2.1]
b130[bundle rhtas-operator v1.3.0]
b131[bundle rhtas-operator v1.3.1]
b132[bundle rhtas-operator v1.3.2]
b130 -->|replaced_by| b131
b130 -->|replaced_by| b132
b131 -.skips.-> b120
b131 -.skips.-> b121
b131 -.skips.-> b130
b132 -.skips.-> b120
b132 -.skips.-> b121
b132 -.skips.-> b130
b132 -.skips.-> b131
end
File-Level Changes
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
![sourcery-ai[bot]](https://avatars.githubusercontent.com/in/48477?s=60&v=4){kind=small}
There was a problem hiding this comment.
Hey there - I've reviewed your changes - here's some feedback:
- In the new 1.3.2 channel entries, consider whether
replacesshould point to v1.3.1 instead of v1.3.0 (with 1.3.0 inskips) to keep the upgrade graph linear and more closely aligned with how previous patches were chained. - Double-check that the updated catalog.json files reference the same 1.3.2 bundle image digest and channel metadata as the corresponding graph.yaml entries to avoid mismatches between the FBC graph and catalog content.
Prompt for AI Agents
Please address the comments from this code review:
## Overall Comments
- In the new 1.3.2 channel entries, consider whether `replaces` should point to v1.3.1 instead of v1.3.0 (with 1.3.0 in `skips`) to keep the upgrade graph linear and more closely aligned with how previous patches were chained.
- Double-check that the updated catalog.json files reference the same 1.3.2 bundle image digest and channel metadata as the corresponding graph.yaml entries to avoid mismatches between the FBC graph and catalog content.Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.
JasonPowr
force-pushed
the
RHTAS-build-bot_candidate-images-main
branch
from
c32e86b to
043c264
Compare
JasonPowr
force-pushed
the
RHTAS-build-bot_candidate-images-main
branch
from
043c264 to
fc1a67e
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 This is an automated PR that updates the FBCs to their latest versions.
Summary by Sourcery
New Features: